docs(extensions): register Compliance Gate Extension v1 — admission-time sanctions/KYC gate RPC method#1886
Open
chopmob-cloud wants to merge 5 commits into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request adds the Compliance Gate Extension to the extensions documentation. The reviewer suggested a minor spelling correction to change 'canonicalised' to 'canonicalized' to maintain consistency with the US English spelling used throughout the document.
| | [Hello World or Timestamp Extension](https://github.com/a2aproject/a2a-samples/tree/main/extensions/timestamp) | A simple extension demonstrating how to augment base A2A types by adding timestamps to the `metadata` field of `Message` and `Artifact` objects (v1). | | ||
| | [Traceability Extension](https://github.com/a2aproject/a2a-samples/tree/main/samples/python/extensions/traceability) | Explore the Python implementation and basic usage of the Traceability Extension (v1). | | ||
| | [Agent Gateway Protocol (AGP) Extension](https://github.com/a2aproject/a2a-samples/tree/main/extensions/agp) | A Core Protocol Layer or Routing Extension that introduces Autonomous Squads (ASq) and routes Intent payloads based on declared Capabilities, enhancing scalability (v1). | | ||
| | [Compliance Gate Extension](https://docs.algovoi.co.uk/compliance-gate-v1) | An AlgoVoi-authored Method Extension adding the `compliance/gate` RPC method. Returns a categorical admission-time sanctions/KYC verdict (`ALLOW` / `REFER` / `DENY`) as a seven-field Compliance Receipt canonicalised under RFC 8785 (JCS). Companion IETF I-D: [`draft-hopley-x402-compliance-receipt`](https://datatracker.ietf.org/doc/draft-hopley-x402-compliance-receipt/) (v1). | |
Contributor
There was a problem hiding this comment.
To maintain spelling consistency with the rest of the document (which uses US English spelling, e.g., 'personalization' on line 49 and 'authorization' on line 278), 'canonicalised' should be spelled as 'canonicalized'.
Suggested change
| | [Compliance Gate Extension](https://docs.algovoi.co.uk/compliance-gate-v1) | An AlgoVoi-authored Method Extension adding the `compliance/gate` RPC method. Returns a categorical admission-time sanctions/KYC verdict (`ALLOW` / `REFER` / `DENY`) as a seven-field Compliance Receipt canonicalised under RFC 8785 (JCS). Companion IETF I-D: [`draft-hopley-x402-compliance-receipt`](https://datatracker.ietf.org/doc/draft-hopley-x402-compliance-receipt/) (v1). | | |
| | [Compliance Gate Extension](https://docs.algovoi.co.uk/compliance-gate-v1) | An AlgoVoi-authored Method Extension adding the `compliance/gate` RPC method. Returns a categorical admission-time sanctions/KYC verdict (`ALLOW` / `REFER` / `DENY`) as a seven-field Compliance Receipt canonicalized under RFC 8785 (JCS). Companion IETF I-D: [`draft-hopley-x402-compliance-receipt`](https://datatracker.ietf.org/doc/draft-hopley-x402-compliance-receipt/) (v1). | |
This was referenced May 30, 2026
…ime sanctions/KYC gate RPC method Adds a single row to the example extensions table in docs/topics/extensions.md pointing at the AlgoVoi-authored Compliance Gate Extension v1 canonical specification at https://docs.algovoi.co.uk/compliance-gate-v1. The extension is a Method Extension defining the compliance/gate RPC method. The method returns a categorical admission-time verdict (ALLOW / REFER / DENY) as a seven-field Compliance Receipt canonicalised under RFC 8785 (JCS). Companion IETF Internet-Draft: draft-hopley-x402-compliance-receipt (Independent Submission, Informational, on IETF datatracker). No new files in the A2A tree. No code changes. No samples. No changes to existing extension entries.
Adds project terms used in the new example extensions row: algovoi, AlgoVoi, Voi, KYC, hopley, chopmob, JCS, datatracker, MiCA, OFSI, OFAC, SAMLA, canonicalisation, canonicalised, unrecognised, unauthorised, tipping, recurr.
A2A check-spelling rejects CamelCase entries (AlgoVoi, MiCA) under the forbidden-pattern rule. Split into components: Algo+Voi, Mi+CA, which the action recognises individually.
'canonicalised' -> 'canonicalized' (matches existing 'personalization', 'authorization' in docs/topics/extensions.md)
chopmob-cloud
force-pushed
the
docs-extensions-add-compliance-gate-v1
branch
from
0b72754 to
d1212b8
Compare
…-compliance-gate-v1 # Conflicts: # .github/actions/spelling/expect.txt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1887.
Summary
Registers the AlgoVoi-authored Compliance Gate Extension (v1) in the A2A
example extensions list.
The extension defines an RPC method
compliance/gatethat anyA2A-conformant agent MAY implement to expose an admission-time
compliance check endpoint. The method returns a categorical verdict
(
ALLOW,REFER,DENY) bound to the request bysha256:referenceunder RFC 8785 (JCS) canonicalisation.
Extension URI:
https://docs.algovoi.co.uk/compliance-gate-v1The extension specification itself is hosted at the AlgoVoi-controlled
URI and is the canonical artefact. This PR adds a single row to the
example extensions table in
docs/topics/extensions.mdpointing at theURI. No code changes. No samples added to the A2A tree. No changes to
existing extension entries.
Why A2A benefits from this
A2A's Extension URI mechanism (per
docs/topics/extensions.md) isdesigned precisely for this shape of contribution: anyone may author,
publish, and implement an extension identified by URI. Agent-to-agent
payment authorisation flows currently have no first-class way to obtain
a regulator-recognised admission-time decision (sanctions screening,
jurisdiction filtering, KYC verification) before mandate construction.
This extension fills that gap with a minimal Method Extension that
composes cleanly with payment-mandate primitives.
The example extensions table already includes domain-specific extensions
(Secure Passport, Timestamp, Traceability, AGP). The Compliance Gate
Extension fits the same pattern as a regulator-discipline extension for
agents operating in regulated payment flows.
Production reference
The endpoint shape and verdict format are generated in production by
the AlgoVoi facilitator at
api.algovoi.co.uk/compliance/screen,live since 2026-05-06 across eight chain families. Documentation:
docs.algovoi.co.uk/platform/compliance-engine.Public audit verifier:
docs.algovoi.co.uk/audit-verifier.This is not a theoretical extension. The endpoint described in this
specification has been serving live admission-time gate checks for
over three weeks.
Authorship and substrate-author position
This extension is sole AlgoVoi authorship across extension URI,
endpoint shape, verdict enumeration, canonicalisation discipline, and
the composition with the AlgoVoi-authored canonicalisation pin and
Compliance Receipt format.
Companion IETF Internet-Draft:
draft-hopley-x402-compliance-receipt(Independent Submission, Informational, on IETF datatracker).
Reference implementation, AlgoVoi-authored, Apache 2.0:
algovoi-substrateon PyPI@algovoi/substrateon npmCross-validated 192-of-192 byte-for-byte across eight independent
language implementations (Python, TypeScript, Go, Rust, Java, PHP, .NET,
Ruby). Conformance corpus:
chopmob-cloud/algovoi-jcs-conformance-vectors.The verdict enumeration is closed by design and may be amended only
by a normative successor extension authored by AlgoVoi or with explicit
AlgoVoi co-authorship. Re-publication of this extension under a
different URI or attribution does not constitute substrate authorship
of the elements defined here.
The extension URI is AlgoVoi-controlled
(
docs.algovoi.co.uk/compliance-gate-v1). Resolution of the URI issolely under AlgoVoi control; A2A's registration in the example
extensions list is a pointer to the canonical specification, not a
re-hosting of it.
No coalition acknowledgements. This extension does not absorb from,
depend on, or share authorship with any other party's work.
Orthogonality
This extension defines the verdict format and gate endpoint at the
admission-time sanctions and KYC screening layer. It is orthogonal
to counterparty-risk evidence endpoints, settlement-attestation
endpoints, agent identity verification, reputation scoring, trust
scoring, composable trust evidence formats, and behavioural attestation
extensions proposed elsewhere as A2A extensions. The Compliance Gate
Extension makes no claims about, and depends on no fields from, any of
the above.
A calling agent that combines a Compliance Gate verdict with other
attestation extensions does so at the calling agent's discretion; this
extension specifies nothing about the combination.
Scope
Single addition to the example extensions table in
docs/topics/extensions.md. No new files in the A2A tree. No codechanges. No samples. No changes to existing extension entries.
-- AlgoVoi (chopmob-cloud)
https://docs.algovoi.co.uk/acquisition